This chapter discusses concepts and tasks for managing the SpinServers in a cluster. The SpinServer provides management utilities for the following components:
Machine information and identification
Internal RAID sets
SpinFS software
Startup images
File-system partitions
Fibre Channel interfaces
Health monitoring
Time setting
Firewall configuration of management and server ports
To control the amount of system resources that are being used, you can also manage long-running jobs, including the VFS copy, delete, move, and mirror operations.
The SpinServer carries identification information that you can set to uniquely identify it in your environment; for instance, you can assign a specific asset tag to it and list its physical location. You can also restart and shut down a SpinServer. Use spinservers commands to perform these operations.
The SpinServer includes two internal RAID sets that are used to hold and run the SpinFS software. Each RAID set is considered a separate file-system partition, and each can hold a separate software image; you can toggle between the images that are used to start the SpinServer. Additionally, you can upgrade the software on one or both RAID sets and manage the file-system partitions that they contain. Use the system commands to perform these operations.
Several VFS operations can take a considerable length of time to complete. These include the copy, move, and mirror operations. Long-running jobs consume a large amount of system resources. To control the use of system resources, you can manage these jobs by using the jobs command node.
Managing SpinServers includes the following tasks:
Displaying information about a SpinServer
Changing identification information for a SpinServer
Restarting a SpinServer
Shutting down a SpinServer
Displaying information about a SpinServer's internal RAID sets
Displaying information about a SpinServer's software
Upgrading a SpinServer's software
Managing a SpinServer's startup images
Managing a SpinServer's internal file-system partitions
Managing the Fibre Channel interface
Managing long-running jobs
Managing health monitoring
Setting and maintaining the time
Configuring the firewall settings for the management and server ports
The spinservers show command displays information about a specific SpinServer (if the -ssid parameter is used) or about all SpinServers in the cluster (if no parameter is used). The following information about the SpinServer or SpinServers is displayed:
SpinServer ID
Owner
Contact information
Serial number
Asset tag
Location
System uptime
System time
Time zone
The command has the following syntax:
spinservers show [-ssid spinserver]
The following example displays information about a SpinServer named Server1.
spinserver::> spinservers show -ssid Server1 SpinServer ID Server1 Owner acmebricks Contact Info it@acmebricks.com Serial Number 2106-0005-01-33021234 Asset Tag 123-456-789 Location Central lab System Uptime 30 days 14 hr 23 min 05 sec System Time 13:30:00 TimeZone US/Eastern
To modify the configuration information for SpinServer, use the spinservers modify command. The command has the following syntax:
spinservers modify -ssid spinserver [-ownername owner_name] [-contact contact_information] [-assettag asset_tag] [-location location] [-tz time_zone] [-systime system_time]
Important: Do not modify the SpinServer ID or host name. To do so invalidates the failover port designation for the SpinServer and can result in the loss of data.
You can modify the owner, contact information, asset tag, location listing, and time zone. These changes do not affect data storage on the system. You can set the time manually on a SpinServer by using the -systime parameter. The argument of the -systime parameter must be in the form YYYY/MM/DD HH:MM:SS, with all zeroes included.
The following command example modifies the contact information for the SpinServer named Server1 so that the owner is listed as acmebricks, the contact is listed as engineering@acmebricks.com, the asset tag is listed as 1234-ABCD, and the location is listed as 3rd_floor_lab. The time is set to midnight on 1 January 2004.
spinserver::> spinservers modify -ssid Server1 -ownername acmebricks -contact engineering@acmebricks.com -assettag 1234-ABCD -location 3rd_floor_lab -systime 2004/01/01 00:00:00
To restart a SpinServer, use the spinservers reboot command. The command has the following syntax:
spinservers reboot -ssid spinserver
The SpinServer prompts you for confirmation after you issue this command. Before restarting the SpinServer, the command saves support data to assist with possible troubleshooting. The restart reason is written to the event log and is displayed in the subsequent startup message.
The following example restarts a SpinServer named Server0 and gives a restart reason of 'spinfs upgrade'.
spinserver::> spinservers reboot -ssid Server0 -rebootreason 'spinfs upgrade'
To shut down a SpinServer, use the spinservers shutdown command. The command has the following syntax:
spinservers shutdown -ssid spinserver -shutdownreason reason_for_shutdown
The SpinServer prompts you for confirmation after you issue this command. Before shutting down the SpinServer, the command saves support data to assist with possible troubleshooting. The shutdown reason is written to the event log and is displayed in the subsequent startup message
The following command example shuts down a SpinServer named Server0 with a reason of 'system maintenance'.
spinserver::> spinservers reboot -ssid Server0 -shutdownreason 'system maintenance'
The system raidsets show command displays information about a SpinServer's internal RAID sets. The command has the following syntax:
system raidsets show [-ssid spinserver -devid device_ID]
Use the command without any parameters to display information about both RAID sets, or with the -ssid and -devid parameters to display information about a specified RAID set. The information for all RAID sets includes the following:
SpinServer ID
Device ID
Status
Whether the RAID set is read-only
Whether Disk0 is operational or faulty
Whether Disk1 is operational or faulty
Resynchronization status
Percentage of RAID set used
The display for a specific RAID set includes the following additional information:
Description
RAID level
Number of blocks
Number of disks
Number of operating disks
Disk0 name
Disk1 name
Whether a resynchronization is in progress
Note: This command applies only to the SpinServer's internal RAID sets. It does not apply to SpinStor RAID or JBOD disk enclosures that are externally connected to the SpinServer.
The following example displays information about an internal RAID set named md1 on a SpinServer named Server1:
spinserver::> system raidsets show -ssid Server1 -devid md1 SpinServer ID Server1 Device ID md1 Description Internal RAID Set md1 RAID Level raid1 Status active Read Only false Blocks 1052160 Disks 2 Operating Disks 2 Disk0 Name sda2 Disk0 Operational true Disk0 Faulty false Disk1 Name sdb2 Disk1 Operational true Disk1 Faulty false Resync In Progress false Resync Status
Use the system software show command to display information about the software packages installed on the SpinServer system. It displays the following information:
SpinServer ID
Package name
Version number
Build number
Installation time
Summary description
The command has the following syntax:
system software show [-ssid spinserver -name software_package]
The following example displays information about all software packages:
spinserver::> system software show
SpinServer ID Pkg Name Version Build Install Time
Server1 spinvldb 2.0.0 32923 11/5/02 2:16 PM
Server1 spinsyslogd 2.0.0 32923 11/5/02 2:16 PM
Server1 modutils 2.4.2 5 3/5/02 10:38 AM
Server1 spinrdb 2.0.0 32923 11/5/02 2:16 PM
Server1 libstdc++ 2.96 81 3/5/02 10:38 AM
Server1 spinsnmp 2.0.0 32923 11/5/02 2:16 PM
Server1 spinmgmt 2.0.0 32923 11/5/02 2:17 PM
Server1 spinfs 2.0.0 32923 11/5/02 2:16 PM
Server1 spinndmpd 2.0.0 32923 11/5/02 2:16 PM
Server1 spingcjlib 3.1.0 32923 11/5/02 2:16 PM
Server1 kernel 2.2.17spinos 32923 11/5/02 2:16 PM
Server1 spindiags 2.0.0 32923 11/5/02 2:16 PM
Server1 glibc 2.2.4 19.3 3/5/02 10:38 AM
To upgrade a SpinServer's base SpinFS software, use the system rootfilesystem upgradesoftware command. The command has the following syntax:
system rootfilesystem upgradesoftware -ssid spinserver -name file_system_name -installurl {cdrom | file:file_name | ftp:FTP_site}
See the Release Notes for the latest software release for complete instructions on upgrading to that release.
To forcibly update a SpinServer's SpinFS software, use the tools system rootfilesystem forceupgrade command. The command has the following syntax:
tools system rootfilesystem forceupgrade -ssid spinserver -name file_system_name -installurl {cdrom | file:file_name | ftp:FTP_site}
Use this command only at the direction of support personnel.
As of SpinFS 2.x, .readwrite mountpoints are used in VFSs to enable certain SpinFS features. These mountpoints do not exist in SpinFS 1.x. If you upgrade a SpinServer from SpinFS 1.x to 2.x, you must create .readwrite mountpoints in each VFS by using the tools filestorage vfs makereadwritemountpoints command.
Use this command only with the assistance of support personnel.
The command has the following syntax:
tools filestorage vfs makereadwritemountpoints -vfsname VFS_name
The following example creates .readwrite mountpoints in a VFS named vfs1 on a SpinServer that was upgraded from SpinFS 1.x to 2.x:
spinserver::> tools filestorage vfs makereadwritemountpoints -vfsname vfs1
Each SpinServer includes two startup images. Each image can hold a different software distribution. You can display information about the startup images and select which image is used to start the SpinServer. This is useful when upgrading software; for instance, you can upgrade the software on one startup image, then start up from that image to ensure that everything works correctly before applying the upgrade globally.
To display information about startup images, use the system bootimages show command. The command has the following syntax:
system bootimages show [-ssid spinserver -label boot_image]
The following example displays information about both startup images on a SpinServer:
spinserver::> system bootimages show
SpinServer ID Label Path Device Current Default
Server1 image1 /boot/vmlinuz /dev/sda2 false false
Server1 image2 /boot/vmlinuz /dev/sda2 true true
To set the default startup image, use the system bootimages setdefault command. The command has the following syntax:
system bootimages setdefault -ssid spinserver -label boot_image
The following example sets the default startup image to image2 on a SpinServer named Server1:
spinserver::> system bootimages setdefault -ssid Server1 -label image2
Each SpinServer system has two root file-system partitions named ROOT and ALTROOT. The SpinFS software is installed on these partitions. The partitions typically remain synchronized, but they can become unsynchronized following a software upgrade or other major maintenance operation. Use the system rootfilesystem commands to work with root file-system partitions.
Use the system rootfilesystem show command to display information about one or both root file-system partitions on a SpinServer. The command has the following syntax:
system rootfilesystem show [-ssid spinserver -name file_system_name]
The following command displays information about the ROOT root file-system partition on a SpinServer named Server1:
spinserver::> system rootfilesystem show -ssid Server1 -name ROOT SpinServer ID Server1 Name ROOT Device /dev/md2 Mount Path / Version 2.0.0 BuildNumber 33414 InstallTime 11/14/2002-00:43:37 Last Sync Time UNKNOWN Last Config Sync Time UNKNOWN Sync On Reboot NONE
Use the system rootfilesystem modify command to set the synchronization value for a SpinServer's root file system at the next system restart. Possible values for synchronization include NONE, for no synchronization; CONFIGURATION, to synchronize the configuration of the two root file systems; and FILESYSTEM, to synchronize the two root file systems. After a system restart, this setting is automatically reset to NONE.
The command has the following syntax:
system rootfilesystem modify -ssid spinserver -name file_system_name -synconreboot {NONE | CONFIGURATION | FILESYSTEM}
The following example modifies the root file-system partition named ROOT on a SpinServer named Server1 so that it synchronizes the configuration of the root file system the next time the SpinServer is restarted:
spinserver::> system rootfilesystem modify -ssid Server1 -name ROOT -synconreboot CONFIGURATION
You can use system hardware fibrechannel commands to work with the SpinServer's Fibre Channel interfaces, which connect the SpinServer to FC-AL-based RAID arrays.
Use the system hardware fibrechannel show command to display information about one or more Fibre Channel channels. Information includes the following:
SpinServer ID
Channel number
Whether or not the channel is present
Port type (QL2200 or QL2312)
Topology (N_Port, NL_Port, F_Port, or FL_Port) (specific port only)
Node name
Port name
State of the channel (up or down)
Current data rate
Desired channel mode (LoopOnly, LoopPreferred, PointToPointOnly, or PointToPointPreferred) (specific port only)
The command has the following syntax:
system hardware fibrechannel show [-ssid spinserver -channel channel_number]
The following example displays information about Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel show -ssid Server1 -channel 0 SpinServer ID Server1 Channel 0 Present true Port Type QL2200 Topology NL_Port Node Name 200100e08b25fb27 Port Name 200100e08b25fb27 State Up Current Data Rate 1GB Desired Channel Mode LoopPreferred
Use the system hardware fibrechannel modify command to change the data rate for a Fibre Channel channel. The command has the following syntax:
system hardware fibrechannel modify -ssid spinserver -channel channel_number -desiredrate data_rate
The following example changes the data rate to AUTO (automatic detection) for Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel modify -ssid Server1 -channel 0 -desiredrate AUTO
Use the system hardware fibrechannel setmode command to set the mode for a Fibre Channel interface. The command has the following syntax:
system hardware fibrechannel setmode -ssid spinserver -channel channel_number -mode mode
Possible values for the value of the -mode parameter include LoopOnly, LoopPreferred, PointToPointOnly, and PointToPointPreferred. The default is LoopPreferred.
The following example sets the mode to LoopOnly for Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel setmode -ssid Server1 -channel 0 -mode LoopOnly
Use the system hardware fibrechannel takedown command to disable a Fibre Channel interface. This is useful for maintenance or for diagnosing problems. The command has the following syntax:
system hardware fibrechannel takedown -ssid spinserver -channel channel_number
The following example disables Fibre Channel 2 on a SpinServer named Server1:
spinserver::> system hardware fibrechannel takedown -ssid Server1 -channel 2
If a Fibre Channel interface has been disabled, use the system hardware fibrechannel bringup command to reenable it. The command has the following syntax:
system hardware fibrechannel bringup -ssid spinserver -channel channel_number
The following example reenables Fibre Channel 2 on a SpinServer named Server1:
spinserver::> system hardware fibrechannel bringup -ssid Server1 -channel 2
To reset a Fibre Channel card and all of its interfaces, use the system hardware fibrechannel cardreset command. The command has the following syntax:
system hardware fibrechannel cardreset -ssid spinserver -channel channel_number
The following example resets the Fibre Channel card with channel 0 on a SpinServer named Server1:
spinserver::> system hardware fibrechannel cardreset -ssid Server1 -channel 0
Use the system hardware fibrechannel lipreset command to issue a loop initialization primitive (LIP) reset on the Fibre Channel. This is useful for Fibre Channel discovery and for verifying connections between the SpinServer and third-party storage products. The command has the following syntax:
system hardware fibrechannel lipreset -ssid spinserver -channel channel_number
The following example issues a LIP reset to Fibre Channel 0 on the SpinServer named Server1:
spinserver::> system hardware fibrechannel lipreset -ssid Server1 -channel 0
You can use the jobs command node to manage long-running VFS operations, including copy, delete, move, and mirror. This is useful if a particular job is consuming too many system resources and you want to stop it or pause it until there is less demand on the system.
Use the jobs show command to display information about one or more long-running jobs. The syntax of the command follows:
jobs show [-id job_ID]
The following example displays information about all current long-running jobs:
spinserver::> jobs show Job ID Job Name SpinServer ID Job State Job Progress 148 delete virtual server: vs1 Server1 finished deleting
Use the jobs pause command to suspend a long-running job. A paused job can be restarted by using the jobs resume command. The jobs pause command has the following syntax:
jobs pause -id job_ID
The following example pauses the job with ID 148:
spinserver::> jobs pause -id 148
Use the jobs resume command to resume a long-running job that was suspended by using the jobs pause command. The jobs resume command has the following syntax:
jobs resume -id job_ID
The following example causes the job with ID 148 to resume:
spinserver::> jobs resume -id 148
Use the jobs kill command to stop a long-running job. A job that is stopped with this command cannot be restarted. The command has the following syntax:
jobs kill -id job_ID
The following example stops the job with ID 148:
spinserver::> jobs kill -id 148
You can set up automatic health monitoring of the SpinServer cluster by using the services support configure commands. With automatic health monitoring, periodic email messages about the SpinServer's condition are sent to a specified address.
Use the services support configure modify command to modify the health-monitoring configuration for a SpinServer. The command has the following syntax:
services support configure modify -enabled {true | false} -reportperiod {daily | weekly | monthly } -supportemail email_address
Use the cluster configuration modify command to specify the mail-from address and outbound mail server for a SpinServer cluster. For more information, see Section 8.2.10.
The following example enables health monitoring on a weekly basis and emails the report to support@spinnakernet.com.
spinserver::> services support configure modify -enabled true -reportperiod weekly -supportemail support@spinnakernet.com
The services support configure show command displays the following information about the health-monitoring configuration of a SpinServer:
Whether automatic health monitoring is enabled (true or false)
The period for health-monitoring reports (daily, weekly, or monthly)
The email address to which health reports are sent
The revision number of the current configuration
The following example displays the health-monitoring configuration of a SpinServer:
spinserver::> services support configure show Enabled true Health Report Period daily Support Email Address support@spinnakernet.com Configuration Revision 1
An accurate time setting is critical for the proper operation of the SpinServer. It is recommended that you use a Network Time Protocol (NTP) server to keep all SpinServers in a cluster set to the correct time.
To set the time manually on a SpinServer, use the -systime parameter of the spinservers modify command, as described in Section 20.2.2. The argument of the -systime parameter must be in the form YYYY/MM/DD HH:MM:SS, with all zeroes included. For instance, to set the system time on Server1 to 1:30 p.m. on 1 June 2003, use the following command:
spinserver::> spinservers modify -ssid Server1 -systime 2003/06/01 13:30:00
To configure a SpinServer to use NTP, use the services ntp commands to create a reference to an NTP server and then to modify the SpinServer cluster to use the NTP server.
Use the services ntp servers new command to create a reference to an NTP server. The command has the following syntax:
services ntp servers new -ipaddress IP_address
The following example creates a reference to an NTP server with the IP address 10.1.4.1:
spinserver::> services ntp servers new -ipaddress 10.1.4.1
Use the services ntp servers show command to display the IP addresses of an NTP server or servers. The command has the following syntax:
services ntp servers show [-ipaddress IP_address]
The following example displays the IP addresses of the NTP servers that are used by a SpinServer:
spinserver::> services ntp servers show
IP Address
10.1.4.1
10.2.4.1
Use the services ntp servers delete command to delete a reference to an NTP server. The command has the following syntax:
services ntp servers delete -ipaddress IP_address
The following example deletes the reference to an NTP server with the IP address 10.1.4.1:
spinserver::> services ntp servers delete -ipaddress 10.1.4.1
Use the services ntp configure modify command to modify the NTP configuration for a SpinServer cluster. The command has the following syntax:
services ntp configure modify -clustername cluster_name -enabled {true | false} -usepdcs {true | false} -useclus {true | false}
where
-clustername cluster_name specifies the name of the cluster.
-enabled {true | false} specifies whether or not to use NTP in the cluster. The default is true.
-usepdcs {true | false} specifies whether or not to use the time setting of the Windows primary domain controller (PDC). The default is false.
-useclus {true | false} specifies whether or not to use SpinServers in the cluster as NTP peers. The default is false.
The following example enables the use of NTP in a cluster named Clus1. PDC time is not used, and SpinServers in the cluster are not used as peers.
spinserver::> services ntp configure modify -clustername Clus1 -enabled true -usepdcs false -useclus false
Use the services ntp configure show command to display the NTP configuration for a SpinServer cluster. The command displays the following information:
Cluster name
Whether or not NTP is enabled for the cluster
Whether or not Windows primary domain controller (PDC) time is used for the cluster
Configuration revision number
The command has the following syntax:
services ntp configure show [-clustername cluster_name]
The following example displays information about the use of NTP in a cluster named Clus1.
spinserver::> services ntp configure show -clustername Clus1 Cluster Name Clus1 Enabled true Use PDC Time false Configuration Revision 0
Use the services firewall configure commands to manage access to the SpinServer's management and server ports.
Use the services firewall configuration modify command to modify the firewall configuration on the management and server ports. You can specify whether management is available on the server ports (by default, false), whether file-serving services are available on the server ports (by default, true), and whether file-serving services are available on the management port (by default, true). The command has the following syntax:
services firewall configuration modify -mgmtonservports {true | false} -svcsonservports {true | false} -svcsonmgmtport {true | false}
The following command modifies the configuration such that management is not accessible on server ports, services are accessible on server ports, and services are not available on the management port:
spinserver::> services firewall configuration modify -mgmtonservports false -svcsonservports true -svcsonmgmtport false
The services firewall configure show command displays access information for the SpinServer's management and server ports. The command displays the following information:
Whether management access is enabled on server ports (true or false)
Whether service access is enabled on server ports (true or false)
Whether service access is enabled on the management port (true or false)
The revision number of the current configuration
spinserver::> services firewall configure show Mgmt On Server Ports false Services On Server Ports true Services On Mgmt Port true Configuration Revision 1
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.